IRIX Base Documentation 2001 May/SGI IRIX Base Documentation 2001 May.iso/usr/share/catman/u_man/cat3/Tk/bind.z/bind

Text File | 1998-10-30 | 32.0 KB | 463 lines

bbbbiiiinnnndddd((((3333TTTTkkkk))))                                                            bbbbiiiinnnndddd((((3333TTTTkkkk))))



NNNNAAAAMMMMEEEE
     bind - Arrange for X events to invoke Tcl scripts

SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
     bbbbiiiinnnndddd _t_a_g
     bbbbiiiinnnndddd _t_a_g _s_e_q_u_e_n_c_e
     bbbbiiiinnnndddd _t_a_g _s_e_q_u_e_n_c_e _s_c_r_i_p_t
     bbbbiiiinnnndddd _t_a_g _s_e_q_u_e_n_c_e ++++_s_c_r_i_p_t


IIIINNNNTTTTRRRROOOODDDDUUUUCCCCTTTTIIIIOOOONNNN
     The bbbbiiiinnnndddd command associates Tcl scripts with X events.  If all three
     arguments are specified, bbbbiiiinnnndddd will arrange for _s_c_r_i_p_t (a Tcl script) to
     be evaluated whenever the event(s) given by _s_e_q_u_e_n_c_e occur in the
     window(s) identified by _t_a_g.  If _s_c_r_i_p_t is prefixed with a ``+'', then it
     is appended to any existing binding for _s_e_q_u_e_n_c_e;  otherwise _s_c_r_i_p_t
     replaces any existing binding.  If _s_c_r_i_p_t is an empty string then the
     current binding for _s_e_q_u_e_n_c_e is destroyed, leaving _s_e_q_u_e_n_c_e unbound.  In
     all of the cases where a _s_c_r_i_p_t argument is provided, bbbbiiiinnnndddd returns an
     empty string.

     If _s_e_q_u_e_n_c_e is specified without a _s_c_r_i_p_t, then the script currently
     bound to _s_e_q_u_e_n_c_e is returned, or an empty string is returned if there is
     no binding for _s_e_q_u_e_n_c_e.  If neither _s_e_q_u_e_n_c_e nor _s_c_r_i_p_t is specified,
     then the return value is a list whose elements are all the sequences for |
     which there exist bindings for _t_a_g.                                      |

     The _t_a_g argument determines which window(s) the binding applies to.  If  |
     _t_a_g begins with a dot, as in ....aaaa....bbbb....cccc, then it must be the path name for a |
     window; otherwise it may be an arbitrary string.  Each window has an     |
     associated list of tags, and a binding applies to a particular window if |
     its tag is among those specified for the window.  Although the bbbbiiiinnnnddddttttaaaaggggssss  |
     command may be used to assign an arbitrary set of binding tags to a      |
     window, the default binding tags provide the following behavior:

          If a tag is the name of an internal window the binding applies to
          that window.

          If the tag is the name of a toplevel window the binding applies to
          the toplevel window and all its internal windows.

          If the tag is the name of a class of widgets, such as BBBBuuuuttttttttoooonnnn, the
          binding applies to all widgets in that class;

          If _t_a_g has the value aaaallllllll, the binding applies to all windows in the
          application.


EEEEVVVVEEEENNNNTTTT PPPPAAAATTTTTTTTEEEERRRRNNNNSSSS
     The _s_e_q_u_e_n_c_e argument specifies a sequence of one or more event patterns,
     with optional white space between the patterns.  Each event pattern may
     take either of two forms.  In the simplest case it is a single printing



                                                                        PPPPaaaaggggeeee 1111






bbbbiiiinnnndddd((((3333TTTTkkkk))))                                                            bbbbiiiinnnndddd((((3333TTTTkkkk))))



     ASCII character, such as aaaa or [[[[.  The character may not be a space
     character or the character <<<<.  This form of pattern matches a KKKKeeeeyyyyPPPPrrrreeeessssssss
     event for the particular character.  The second form of pattern is longer
     but more general.  It has the following syntax:

          <<<<_m_o_d_i_f_i_e_r-_m_o_d_i_f_i_e_r-_t_y_p_e-_d_e_t_a_i_l>>>>

     The entire event pattern is surrounded by angle brackets.  Inside the
     angle brackets are zero or more modifiers, an event type, and an extra
     piece of information (_d_e_t_a_i_l) identifying a particular button or keysym.
     Any of the fields may be omitted, as long as at least one of _t_y_p_e and
     _d_e_t_a_i_l is present.  The fields must be separated by white space or
     dashes.


MMMMOOOODDDDIIIIFFFFIIIIEEEERRRRSSSS
     Modifiers consist of any of the following values:                        |

          CCCCoooonnnnttttrrrroooollll                 MMMMoooodddd2222,,,, MMMM2222                                    |
          SSSShhhhiiiifffftttt                   MMMMoooodddd3333,,,, MMMM3333                                    |
          LLLLoooocccckkkk                    MMMMoooodddd4444,,,, MMMM4444                                    |
          BBBBuuuuttttttttoooonnnn1111,,,, BBBB1111             MMMMoooodddd5555,,,, MMMM5555                                    |
          BBBBuuuuttttttttoooonnnn2222,,,, BBBB2222             MMMMeeeettttaaaa,,,, MMMM                                     |
          BBBBuuuuttttttttoooonnnn3333,,,, BBBB3333             AAAAlllltttt                                         |
          BBBBuuuuttttttttoooonnnn4444,,,, BBBB4444             DDDDoooouuuubbbblllleeee                                      |
          BBBBuuuuttttttttoooonnnn5555,,,, BBBB5555             TTTTrrrriiiipppplllleeee                                      |
          MMMMoooodddd1111,,,, MMMM1111                                                            |

     Where more than one value is listed, separated by commas, the values are |
     equivalent.  Most of the modifiers have the obvious X meanings.  For     |
     example, BBBBuuuuttttttttoooonnnn1111 requires that button 1 be depressed when the event      |
     occurs.  For a binding to match a given event, the modifiers in the event|
     must include all of those specified in the event pattern.  An event may  |
     also contain additional modifiers not specified in the binding.  For     |
     example, if button 1 is pressed while the shift and control keys are     |
     down, the pattern <<<<CCCCoooonnnnttttrrrroooollll----BBBBuuuuttttttttoooonnnn----1111>>>> will match the event, but <<<<MMMMoooodddd1111----    |
     BBBBuuuuttttttttoooonnnn----1111>>>> will not.  If no modifiers are specified, then any combination |
     of modifiers may be present in the event.                                |

     MMMMeeeettttaaaa and MMMM refer to whichever of the MMMM1111 through MMMM5555 modifiers is          |
     associated with the meta key(s) on the keyboard (keysyms MMMMeeeettttaaaa____RRRR and      |
     MMMMeeeettttaaaa____LLLL).  If there are no meta keys, or if they are not associated with  |
     any modifiers, then MMMMeeeettttaaaa and MMMM will not match any events.  Similarly, the|
     AAAAlllltttt modifier refers to whichever modifier is associated with the alt     |
     key(s) on the keyboard (keysyms AAAAlllltttt____LLLL and AAAAlllltttt____RRRR).

     The DDDDoooouuuubbbblllleeee and TTTTrrrriiiipppplllleeee modifiers are a convenience for specifying double
     mouse clicks and other repeated events. They cause a particular event
     pattern to be repeated 2 or 3 times, and also place a time and space
     requirement on the sequence:  for a sequence of events to match a DDDDoooouuuubbbblllleeee
     or TTTTrrrriiiipppplllleeee pattern, all of the events must occur close together in time
     and without substantial mouse motion in between.  For example, <<<<DDDDoooouuuubbbblllleeee----



                                                                        PPPPaaaaggggeeee 2222






bbbbiiiinnnndddd((((3333TTTTkkkk))))                                                            bbbbiiiinnnndddd((((3333TTTTkkkk))))



     BBBBuuuuttttttttoooonnnn----1111>>>> is equivalent to <<<<BBBBuuuuttttttttoooonnnn----1111>>>><<<<BBBBuuuuttttttttoooonnnn----1111>>>> with the extra time and
     space requirement.


EEEEVVVVEEEENNNNTTTT TTTTYYYYPPPPEEEESSSS
     The _t_y_p_e field may be any of the standard X event types, with a few extra
     abbreviations.  Below is a list of all the valid types; where two names
     appear together, they are synonyms.

          BBBBuuuuttttttttoooonnnnPPPPrrrreeeessssssss,,,, BBBBuuuuttttttttoooonnnn EEEExxxxppppoooosssseeee             MMMMaaaapppp                          |
          BBBBuuuuttttttttoooonnnnRRRReeeelllleeeeaaaasssseeee       FFFFooooccccuuuussssIIIInnnn            MMMMoooottttiiiioooonnnn                       |
          CCCCiiiirrrrccccuuuullllaaaatttteeee           FFFFooooccccuuuussssOOOOuuuutttt           PPPPrrrrooooppppeeeerrrrttttyyyy                     |
          CCCCoooolllloooorrrrmmmmaaaapppp            GGGGrrrraaaavvvviiiittttyyyy            RRRReeeeppppaaaarrrreeeennnntttt                     |
          CCCCoooonnnnffffiiiigggguuuurrrreeee           KKKKeeeeyyyyPPPPrrrreeeessssssss,,,, KKKKeeeeyyyy      UUUUnnnnmmmmaaaapppp                        |
          DDDDeeeessssttttrrrrooooyyyy             KKKKeeeeyyyyRRRReeeelllleeeeaaaasssseeee         VVVViiiissssiiiibbbbiiiilllliiiittttyyyy                   |
          EEEEnnnntttteeeerrrr               LLLLeeeeaaaavvvveeee


     The last part of a long event specification is _d_e_t_a_i_l.  In the case of a
     BBBBuuuuttttttttoooonnnnPPPPrrrreeeessssssss or BBBBuuuuttttttttoooonnnnRRRReeeelllleeeeaaaasssseeee event, it is the number of a button (1-5).
     If a button number is given, then only an event on that particular button
     will match;  if no button number is given, then an event on any button
     will match.  Note:  giving a specific button number is different than
     specifying a button modifier; in the first case, it refers to a button
     being pressed or released, while in the second it refers to some other
     button that is already depressed when the matching event occurs.  If a
     button number is given then _t_y_p_e may be omitted:  if will default to
     BBBBuuuuttttttttoooonnnnPPPPrrrreeeessssssss.  For example, the specifier <<<<1111>>>> is equivalent to
     <<<<BBBBuuuuttttttttoooonnnnPPPPrrrreeeessssssss----1111>>>>.

     If the event type is KKKKeeeeyyyyPPPPrrrreeeessssssss or KKKKeeeeyyyyRRRReeeelllleeeeaaaasssseeee, then _d_e_t_a_i_l may be specified
     in the form of an X keysym.  Keysyms are textual specifications for
     particular keys on the keyboard; they include all the alphanumeric ASCII
     characters (e.g. ``a'' is the keysym for the ASCII character ``a''), plus
     descriptions for non-alphanumeric characters (``comma'' is the keysym for
     the comma character), plus descriptions for all the non-ASCII keys on the
     keyboard (``Shift_L'' is the keysm for the left shift key, and ``F1'' is
     the keysym for the F1 function key, if it exists).  The complete list of
     keysyms is not presented here;  it is available in other X documentation
     and may vary from system to system.  If necessary, you can use the %%%%KKKK
     notation described below to print out the keysym name for a particular
     key.  If a keysym _d_e_t_a_i_l is given, then the _t_y_p_e field may be omitted;
     it will default to KKKKeeeeyyyyPPPPrrrreeeessssssss.  For example, <<<<CCCCoooonnnnttttrrrroooollll----ccccoooommmmmmmmaaaa>>>> is equivalent
     to <<<<CCCCoooonnnnttttrrrroooollll----KKKKeeeeyyyyPPPPrrrreeeessssssss----ccccoooommmmmmmmaaaa>>>>.


BBBBIIIINNNNDDDDIIIINNNNGGGG SSSSCCCCRRRRIIIIPPPPTTTTSSSS AAAANNNNDDDD SSSSUUUUBBBBSSSSTTTTIIIITTTTUUUUTTTTIIIIOOOONNNNSSSS
     The _s_c_r_i_p_t argument to bbbbiiiinnnndddd is a Tcl script, which will be executed
     whenever the given event sequence occurs.  _C_o_m_m_a_n_d will be executed in
     the same interpreter that the bbbbiiiinnnndddd command was executed in, and it will
     run at global level (only global variables will be accessible).  If
     _s_c_r_i_p_t contains any %%%% characters, then the script will not be executed



                                                                        PPPPaaaaggggeeee 3333






bbbbiiiinnnndddd((((3333TTTTkkkk))))                                                            bbbbiiiinnnndddd((((3333TTTTkkkk))))



     directly.  Instead, a new script will be generated by replacing each %%%%,
     and the character following it, with information from the current event.
     The replacement depends on the character following the %%%%, as defined in
     the list below.  Unless otherwise indicated, the replacement string is   |
     the decimal value of the given field from the current event.  Some of the
     substitutions are only valid for certain types of events;  if they are
     used for other types of events the value substituted is undefined.

     %%%%%%%%   Replaced with a single percent.

     %%%%####   The number of the last client request processed by the server (the
          _s_e_r_i_a_l field from the event).  Valid for all event types.

     %%%%aaaa   The _a_b_o_v_e field from the event, formatted as a hexadecimal number.  |
          Valid only for CCCCoooonnnnffffiiiigggguuuurrrreeee events.

     %%%%bbbb   The number of the button that was pressed or released.  Valid only
          for BBBBuuuuttttttttoooonnnnPPPPrrrreeeessssssss and BBBBuuuuttttttttoooonnnnRRRReeeelllleeeeaaaasssseeee events.

     %%%%cccc   The _c_o_u_n_t field from the event.  Valid only for EEEExxxxppppoooosssseeee events.

     %%%%dddd   The _d_e_t_a_i_l field from the event.  The %%%%dddd is replaced by a string
          identifying the detail.  For EEEEnnnntttteeeerrrr, LLLLeeeeaaaavvvveeee, FFFFooooccccuuuussssIIIInnnn, and FFFFooooccccuuuussssOOOOuuuutttt
          events, the string will be one of the following:

               NNNNoooottttiiiiffffyyyyAAAAnnnncccceeeessssttttoooorrrr          NNNNoooottttiiiiffffyyyyNNNNoooonnnnlllliiiinnnneeeeaaaarrrrVVVViiiirrrrttttuuuuaaaallll
               NNNNoooottttiiiiffffyyyyDDDDeeeettttaaaaiiiillllNNNNoooonnnneeee        NNNNoooottttiiiiffffyyyyPPPPooooiiiinnnntttteeeerrrr
               NNNNoooottttiiiiffffyyyyIIIInnnnffffeeeerrrriiiioooorrrr          NNNNoooottttiiiiffffyyyyPPPPooooiiiinnnntttteeeerrrrRRRRooooooootttt
               NNNNoooottttiiiiffffyyyyNNNNoooonnnnlllliiiinnnneeeeaaaarrrr         NNNNoooottttiiiiffffyyyyVVVViiiirrrrttttuuuuaaaallll

          For events other than these, the substituted string is undefined.

     %%%%ffff   The _f_o_c_u_s field from the event (0000 or 1111).  Valid only for EEEEnnnntttteeeerrrr and
          LLLLeeeeaaaavvvveeee events.

     %%%%hhhh   The _h_e_i_g_h_t field from the event.  Valid only for CCCCoooonnnnffffiiiigggguuuurrrreeee, EEEExxxxppppoooosssseeee,
          and GGGGrrrraaaapppphhhhiiiiccccssssEEEExxxxppppoooosssseeee events.

     %%%%kkkk   The _k_e_y_c_o_d_e field from the event.  Valid only for KKKKeeeeyyyyPPPPrrrreeeessssssss and
          KKKKeeeeyyyyRRRReeeelllleeeeaaaasssseeee events.

     %%%%mmmm   The _m_o_d_e field from the event.  The substituted string is one of
          NNNNoooottttiiiiffffyyyyNNNNoooorrrrmmmmaaaallll, NNNNoooottttiiiiffffyyyyGGGGrrrraaaabbbb, NNNNoooottttiiiiffffyyyyUUUUnnnnggggrrrraaaabbbb, or NNNNoooottttiiiiffffyyyyWWWWhhhhiiiilllleeeeGGGGrrrraaaabbbbbbbbeeeedddd.
          Valid only for EEEEnnnntttteeeerrrrWWWWiiiinnnnddddoooowwww, FFFFooooccccuuuussssIIIInnnn, FFFFooooccccuuuussssOOOOuuuutttt, and LLLLeeeeaaaavvvveeeeWWWWiiiinnnnddddoooowwww
          events.

     %%%%oooo   The _o_v_e_r_r_i_d_e__r_e_d_i_r_e_c_t field from the event.  Valid only for MMMMaaaapppp,
          RRRReeeeppppaaaarrrreeeennnntttt, and CCCCoooonnnnffffiiiigggguuuurrrreeee events.

     %%%%pppp   The _p_l_a_c_e field from the event, substituted as one of the strings
          PPPPllllaaaacccceeeeOOOOnnnnTTTToooopppp or PPPPllllaaaacccceeeeOOOOnnnnBBBBoooottttttttoooommmm.  Valid only for CCCCiiiirrrrccccuuuullllaaaatttteeee events.




                                                                        PPPPaaaaggggeeee 4444






bbbbiiiinnnndddd((((3333TTTTkkkk))))                                                            bbbbiiiinnnndddd((((3333TTTTkkkk))))



     %%%%ssss   The _s_t_a_t_e field from the event.  For BBBBuuuuttttttttoooonnnnPPPPrrrreeeessssssss, BBBBuuuuttttttttoooonnnnRRRReeeelllleeeeaaaasssseeee,
          EEEEnnnntttteeeerrrr, KKKKeeeeyyyyPPPPrrrreeeessssssss, KKKKeeeeyyyyRRRReeeelllleeeeaaaasssseeee, LLLLeeeeaaaavvvveeee, and MMMMoooottttiiiioooonnnn events, a decimal    |
          string is substituted.  For VVVViiiissssiiiibbbbiiiilllliiiittttyyyy, one of the strings
          VVVViiiissssiiiibbbbiiiilllliiiittttyyyyUUUUnnnnoooobbbbssssccccuuuurrrreeeedddd, VVVViiiissssiiiibbbbiiiilllliiiittttyyyyPPPPaaaarrrrttttiiiiaaaallllllllyyyyOOOObbbbssssccccuuuurrrreeeedddd, and
          VVVViiiissssiiiibbbbiiiilllliiiittttyyyyFFFFuuuullllllllyyyyOOOObbbbssssccccuuuurrrreeeedddd is substituted.

     %%%%tttt   The _t_i_m_e field from the event.  Valid only for events that contain a
          _t_i_m_e field.

     %%%%wwww   The _w_i_d_t_h field from the event.  Valid only for CCCCoooonnnnffffiiiigggguuuurrrreeee, EEEExxxxppppoooosssseeee,
          and GGGGrrrraaaapppphhhhiiiiccccssssEEEExxxxppppoooosssseeee events.

     %%%%xxxx   The _x field from the event.  Valid only for events containing an _x
          field.

     %%%%yyyy   The _y field from the event.  Valid only for events containing a _y
          field.

     %%%%AAAA   Substitutes the ASCII character corresponding to the event, or the
          empty string if the event doesn't correspond to an ASCII character
          (e.g. the shift key was pressed).  XXXXLLLLooooooookkkkuuuuppppSSSSttttrrrriiiinnnngggg does all the work
          of translating from the event to an ASCII character.  Valid only for
          KKKKeeeeyyyyPPPPrrrreeeessssssss and KKKKeeeeyyyyRRRReeeelllleeeeaaaasssseeee events.

     %%%%BBBB   The _b_o_r_d_e_r__w_i_d_t_h field from the event.  Valid only for CCCCoooonnnnffffiiiigggguuuurrrreeee
          events.

     %%%%EEEE   The _s_e_n_d__e_v_e_n_t field from the event.  Valid for all event types.

     %%%%KKKK   The keysym corresponding to the event, substituted as a textual
          string.  Valid only for KKKKeeeeyyyyPPPPrrrreeeessssssss and KKKKeeeeyyyyRRRReeeelllleeeeaaaasssseeee events.

     %%%%NNNN   The keysym corresponding to the event, substituted as a decimal     |
          number.  Valid only for KKKKeeeeyyyyPPPPrrrreeeessssssss and KKKKeeeeyyyyRRRReeeelllleeeeaaaasssseeee events.

     %%%%RRRR   The _r_o_o_t window identifier from the event.  Valid only for events
          containing a _r_o_o_t field.

     %%%%SSSS   The _s_u_b_w_i_n_d_o_w window identifier from the event, formatted as a      |
          hexadecimal number.  Valid only for events containing a _s_u_b_w_i_n_d_o_w
          field.

     %%%%TTTT   The _t_y_p_e field from the event.  Valid for all event types.

     %%%%WWWW   The path name of the window to which the event was reported (the
          _w_i_n_d_o_w field from the event).  Valid for all event types.

     %%%%XXXX   The _x__r_o_o_t field from the event.  If a virtual-root window manager  |
          is being used then the substituted value is the corresponding x-    |
          coordinate in the virtual root.  Valid only for BBBBuuuuttttttttoooonnnnPPPPrrrreeeessssssss,
          BBBBuuuuttttttttoooonnnnRRRReeeelllleeeeaaaasssseeee, KKKKeeeeyyyyPPPPrrrreeeessssssss, KKKKeeeeyyyyRRRReeeelllleeeeaaaasssseeee, and MMMMoooottttiiiioooonnnn events.




                                                                        PPPPaaaaggggeeee 5555






bbbbiiiinnnndddd((((3333TTTTkkkk))))                                                            bbbbiiiinnnndddd((((3333TTTTkkkk))))



     %%%%YYYY   The _y__r_o_o_t field from the event.  If a virtual-root window manager  |
          is being used then the substituted value is the corresponding y-    |
          coordinate in the virtual root.  Valid only for BBBBuuuuttttttttoooonnnnPPPPrrrreeeessssssss,
          BBBBuuuuttttttttoooonnnnRRRReeeelllleeeeaaaasssseeee, KKKKeeeeyyyyPPPPrrrreeeessssssss, KKKKeeeeyyyyRRRReeeelllleeeeaaaasssseeee, and MMMMoooottttiiiioooonnnn events.

     The replacement string for a %-replacement is formatted as a proper Tcl  |
     list element.  This means that it will be surrounded with braces if it   |
     contains spaces, or special characters such as $$$$ and {{{{ may be preceded by|
     backslashes.  This guarantees that the string will be passed through the |
     Tcl parser when the binding script is evaluated.  Most replacements are  |
     numbers or well-defined strings such as AAAAbbbboooovvvveeee;  for these replacements no|
     special formatting is ever necessary.  The most common case where        |
     reformatting occurs is for the %%%%AAAA substitution.  For example, if _s_c_r_i_p_t  |
     is                                                                       |

          iiiinnnnsssseeeerrrrtttt %%%%AAAA                                                           |

     and the character typed is an open square bracket, then the script       |
     actually executed will be                                                |

          iiiinnnnsssseeeerrrrtttt \\\\[[[[                                                           |

     This will cause the iiiinnnnsssseeeerrrrtttt to receive the original replacement string    |
     (open square bracket) as its first argument.  If the extra backslash     |
     hadn't been added, Tcl would not have been able to parse the script      |
     correctly.


MMMMUUUULLLLTTTTIIIIPPPPLLLLEEEE MMMMAAAATTTTCCCCHHHHEEEESSSS
     It is possible for several bindings to match a given X event.  If the    |
     bindings are associated with different _t_a_g's, then each of the bindings  |
     will be executed, in order.  By default, a class binding will be executed|
     first, followed by a binding for the widget, a binding for its toplevel, |
     and an aaaallllllll binding.  The bbbbiiiinnnnddddttttaaaaggggssss command may be used to change this     |
     order for a particular window or to associate additional binding tags    |
     with the window.                                                         |

     The ccccoooonnnnttttiiiinnnnuuuueeee and bbbbrrrreeeeaaaakkkk commands may be used inside a binding script to   |
     control the processing of matching scripts.  If ccccoooonnnnttttiiiinnnnuuuueeee is invoked, then|
     the current binding script is terminated but Tk will continue processing |
     binding scripts associated with other _t_a_g's.  If the bbbbrrrreeeeaaaakkkk command is    |
     invoked within a binding script, then that script terminates and no other|
     scripts will be invoked for the event.                                   |

     If more than one binding matches a particular event and they have the    |
     same _t_a_g, then the most specific binding is chosen and its script is     |
     evaluated.  The following tests are applied, in order, to determine which|
     of several matching sequences is more specific:  (a) a longer sequence   |
     (in terms of number of events matched) is more specific than a shorter   |
     sequence; (b) an event pattern that specifies a specific button or key is|
     more specific than one that doesn't; (c) if the modifiers specified in   |
     one pattern are a subset of the modifiers in another pattern, then the   |



                                                                        PPPPaaaaggggeeee 6666






bbbbiiiinnnndddd((((3333TTTTkkkk))))                                                            bbbbiiiinnnndddd((((3333TTTTkkkk))))



     pattern with more modifiers is more specific.  If the matching sequences
     contain more than one event, then tests (c)-(e) are applied in order from
     the most recent event to the least recent event in the sequences.  If
     these tests fail to determine a winner, then the most recently registered
     sequence is the winner.

     If an X event does not match any of the existing bindings, then the event
     is ignored.  An unbound event is not considered to be an error.


MMMMUUUULLLLTTTTIIII----EEEEVVVVEEEENNNNTTTT SSSSEEEEQQQQUUUUEEEENNNNCCCCEEEESSSS AAAANNNNDDDD IIIIGGGGNNNNOOOORRRREEEEDDDD EEEEVVVVEEEENNNNTTTTSSSS
     When a _s_e_q_u_e_n_c_e specified in a bbbbiiiinnnndddd command contains more than one event
     pattern, then its script is executed whenever the recent events (leading
     up to and including the current event) match the given sequence.  This
     means, for example, that if button 1 is clicked repeatedly the sequence
     <<<<DDDDoooouuuubbbblllleeee----BBBBuuuuttttttttoooonnnnPPPPrrrreeeessssssss----1111>>>> will match each button press but the first.  If   |
     extraneous events that would prevent a match occur in the middle of an   |
     event sequence then the extraneous events are ignored unless they are    |
     KKKKeeeeyyyyPPPPrrrreeeessssssss or BBBBuuuuttttttttoooonnnnPPPPrrrreeeessssssss events.  For example, <<<<DDDDoooouuuubbbblllleeee----BBBBuuuuttttttttoooonnnnPPPPrrrreeeessssssss----1111>>>> will|
     match a sequence of presses of button 1, even though there will be       |
     BBBBuuuuttttttttoooonnnnRRRReeeelllleeeeaaaasssseeee events (and possibly MMMMoooottttiiiioooonnnn events) between the BBBBuuuuttttttttoooonnnnPPPPrrrreeeessssssss|
     events.  Furthermore, a KKKKeeeeyyyyPPPPrrrreeeessssssss event may be preceded by any number of  |
     other KKKKeeeeyyyyPPPPrrrreeeessssssss events for modifier keys without the modifier keys        |
     preventing a match.  For example, the event sequence aaaaBBBB will match a     |
     press of the aaaa key, a release of the aaaa key, a press of the SSSShhhhiiiifffftttt key, and|
     a press of the bbbb key:  the press of SSSShhhhiiiifffftttt is ignored because it is a     |
     modifier key.  Finally, if several MMMMoooottttiiiioooonnnn events occur in a row, only the
     last one is used for purposes of matching binding sequences.


EEEERRRRRRRROOOORRRRSSSS
     If an error occurs in executing the script for a binding then the ttttkkkkeeeerrrrrrrroooorrrr
     mechanism is used to report the error.  The ttttkkkkeeeerrrrrrrroooorrrr command will be      |
     executed at global level (outside the context of any Tcl procedure).


SSSSEEEEEEEE AAAALLLLSSSSOOOO
     tkerror


KKKKEEEEYYYYWWWWOOOORRRRDDDDSSSS
     form, manual













                                                                        PPPPaaaaggggeeee 7777